Portable device for logging driving information

ABSTRACT

Methods, systems, and devices for logging performance of a driver operating a commercial motor vehicle (“CMV”). One method includes receiving at a portable device identifying information for the driver through a graphical user interface and at least one operating parameter from a non-portable base unit installed in the CMV. The non-portable base unit includes a processor and non-transitory computer-readable medium and configured to monitor at least one operating parameter of the CMV. The method also includes determining compliance data at the portable device based, at least in part, on the identifying information and the at least one operating parameter, and wirelessly transmitting signals based on the compliance data from the portable device to a remote host.

RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.13/852,788, filed on Mar. 28, 2013, which is a continuation of U.S.application Ser. No. 12/027,021, filed on Feb. 6, 2008, which claims thebenefit of U.S. Provisional Application No. 60/888,458, filed on Feb. 6,2007, the entire contents of which are both incorporated by referenceherein.

BACKGROUND

Embodiments of the invention relate to systems and methods forcomputerized management of operators of commercial vehicles.

Operators of commercial motor vehicles (“CMV's”) are required to meetcertain specific performance standards and regulations for operatingsuch vehicles. For example, some operators of the CMV's are required tomeet hours-of-service regulations.

The U.S. Department of Transportation, Federal Motor Carrier SafetyAdministration (“FMCSA”) has established a comprehensive list ofregulations that professional operators of CMV's must comply with. Theseregulations govern drivers, CMV or trucking companies (sometimes called“carriers”) and the CMV's belonging to the carriers. Professionaloperators must comply with the obligations imposed under federal andstate requirements in these areas. The regulations not only includephysical and age requirements, but also define the ways an operator canlose his commercial driving privileges. Trucking companies and companieshaving trucking operations that support their core business aretypically required to evaluate and track many aspects of truck operatorsand their abilities to perform job tasks such as driver qualifications(such as operator licensing and renewal); alcohol and drug testing;accident reporting; driver training; and hiring and screening ofapplicants.

Many CMV's are equipped with electronic-on-board-recorders to recordinformation relating to the CMV's. The information generally includesnames of the carriers, and the U.S. Department of Transportation numberof the CMV's. For compliance purposes, operators of the CMV's are alsofrequently required to collect other relevant information of the driverssuch as name, duty status, date and time, locations of the CMV's, anddistance traveled. As part of the standards and/or regulations, theoperators are required to submit the collected information. Operatorsfrequently submit the collected information on paper. Paper-basedprocesses are often slow. As a result, important compliance informationmight not be received in time to enforce certain regulatory requirementsor to take other relevant actions based on the information.

SUMMARY

Although, various paper-based systems and software are available toassist CMV carriers with some of the areas noted above, such systems arenot completely satisfactory. Continued growth and regulation of thecarrier industry as well as the increasingly sophisticated logisticalmechanisms used to ensure timely and efficient delivery of goods hasincreased the need of operators to manage their drivers and fleets. Assuch, it is useful for carriers to have systems available for collectingand communicating information relating to tasks which must be performedunder various regulations in order for the company to show that it andits drivers are in compliance. In addition, such information can be usedfor several management purposes and by the operators of such CMV's.

In one embodiment, the invention provides a logging system that includesa vehicle, a portable device, and a remote host. The vehicle includes acontroller and a base unit. The controller is positioned in the vehicle,and monitors one or more operating parameters of the vehicle. The baseunit is mounted in the vehicle, and is connected to the controller toreceive and store the one or more operating parameters from the device.The portable device, typically carried by the driver, can be coupled tothe base unit. Once coupled, the portable device receives identifyinginformation from the driver, receives the one or more operatingparameters from the base unit, determines compliance data based, atleast in part, on the identifying information and the one or moreoperating parameters, and wirelessly transmits signals based on thecompliance data. The remote host is configured to wirelessly receive thesignals from the portable device, and to wirelessly manage the portabledevice based, at least in part, on the received signals.

In another embodiment, the invention provides a system for loggingperformance of a driver operating a vehicle. The system includes a baseunit, a portable device, and a remote host. The base unit is mounted inthe vehicle and is configured to monitor one or more operatingparameters of the vehicle. The portable device can be coupled to thebase unit to receive identifying information from the driver, to receivethe one or more operating parameters from the base unit, to determinecompliance data based, at least in part, on the identifying informationand the one or more operating parameters, and to wirelessly transmitsignals based on the compliance data. The remote host can wirelesslyreceive the signals from the portable device, and wirelessly manage theportable device based, at least in part, on the received signals.

In yet another embodiment, the invention provides a method for loggingperformance of a driver operating a vehicle. The method includesreceiving identifying information from the driver at a portable device,verifying the identifying information from the driver at the portabledevice, and receiving one or more operating parameters from the vehicleat the portable device once the identifying information has beenverified. The method also includes determining compliance informationbased, at least in part, on the identifying information and the one ormore operating parameters at the portable device, wirelesslytransmitting compliance signals indicative of the compliance data fromthe portable device, and wirelessly receiving the compliance signals ata remote host from the portable device. The method also includesgenerating managing signals based on the received signals at the remotehost, wirelessly transmitting the managing signals from the remote hostto the portable device, wirelessly receiving the managing signals at theportable device, and managing performance of the driver and the vehiclebased on the received managing signals.

In still a further embodiment, the invention provides a method forlogging performance of a driver operating a CMV. One method includesreceiving at a portable device identifying information for the driverthrough a graphical user interface and at least one operating parameterfrom a non-portable base unit installed in the CMV. The non-portablebase unit includes a processor and non-transitory computer-readablemedium and configured to monitor at least one operating parameter of theCMV. The method also includes determining compliance data at theportable device based, at least in part, on the identifying informationand the at least one operating parameter, and wirelessly transmittingsignals based on the compliance data from the portable device to aremote host.

The method includes receiving, at a portable device, identifyinginformation for the driver through a graphical user interface,receiving, at the portable device, at least one operating parameter froma non-portable base unit installed in the CMV, the non-portable baseunit including a processor and non-transitory computer-readable mediumand configured to monitor at least one operating parameter of the CMV,and determining compliance data at the portable device based, at leastin part, on the identifying information and the at least one operatingparameter. The method also includes wirelessly transmitting signalsbased on the compliance data from the portable device to a remote host.

In another embodiment, the invention provides a portable device forlogging performance of a driver operating a CMV. The portable deviceincludes a processor and a non-transitory computer-readable medium. Themedium stores instructions executable by the processor to receiveidentifying information for the driver through a graphical userinterface and receive at least one operating parameter from anon-portable base unit installed in the CMV. The non-portable base unitincludes a processor and a non-transitory computer-readable medium andconfigured to monitor at least one operating parameter of the CMV. Themedium also stores instructions to determine compliance data at theportable device based, at least in part, on the identifying informationand the at least one operating parameter, and wirelessly transmitsignals based on the compliance data from the portable device to aremote host.

In yet another embodiment, the invention provides a system for loggingperformance of a driver operating a CMV. The system includes anon-portable base unit installed in the CMV and configured to store atleast one operating parameter of the CMV, and a portable deviceconfigured to receive the at least one operating parameter stored in thenon-portable base unit, determine compliance data based on the at leastone operating parameter, and wirelessly transmit signals based on thecompliance data to a remote host. The non-portable base unit stores theat least one operating parameter until the portable device connects tothe base unit over one of a wired connection and a wireless connectionto receive the at least one operating parameter.

Other aspects of the invention will become apparent by consideration ofthe detailed description and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of a system structured in accordancewith an embodiment of the invention.

FIG. 2 illustrates a base unit of the system in FIG. 1 in a blockdiagram format.

FIG. 3 is a circuit diagram for one embodiment of the base unit of FIG.2.

FIG. 3A is a circuit diagram for an alternative embodiment of the baseunit of FIG. 2.

FIG. 4 shows a portable device in the form of a smart phone displaying alogin screen.

FIG. 5 shows the smart phone of FIG. 4 displaying a trip login screen.

FIG. 6 shows the smart phone of FIG. 4 displaying a location editscreen.

FIG. 7 shows the smart phone of FIG. 4 displaying a time edit screen.

FIG. 8 shows the smart phone of FIG. 4 displaying a status edit screen.

FIG. 9 shows an exemplary status screen of a CMV operated by a CMVdriver.

FIG. 10 shows the smart phone of FIG. 4 displaying a plurality of menufunctions in the status screen of FIG. 9.

FIG. 11 shows the smart phone of FIG. 4 displaying a duty status reportscreen.

FIG. 12 shows the smart phone of FIG. 4 displaying a log detail screendetailing a specific log entry of FIG. 11.

FIG. 13 shows the smart phone of FIG. 4 displaying a log downloadscreen.

FIG. 14 shows the smart phone of FIG. 4 displaying a confirmation screen

FIG. 15 shows the smart phone of FIG. 4 displaying a logout screen.

FIG. 16 shows the smart phone of FIG. 4 displaying a log submissionscreen.

FIG. 17 shows the smart phone of FIG. 4 displaying a log submissioncomplete screen.

FIG. 18 shows an exemplary screen of the remote host application of FIG.1.

DETAILED DESCRIPTION

Before any embodiments of the invention are explained in detail, it isto be understood that the invention is not limited in its application tothe details of construction and the arrangement of components set forthin the following description or illustrated in the following drawings.The invention is capable of other embodiments and of being practiced orof being carried out in various ways.

In one particular embodiment, the invention provides a system forlogging performance of a driver operating a vehicle having a vehicleinformation system from which at least one vehicle operating parametermay be obtained in a performance monitoring process. The vehicleoperating parameter collected through the vehicle information system andinformation such as operator identity from a portable device arewirelessly communicated to a remote host through a network such as theInternet.

FIG. 1 shows a performance monitoring system 100 for use with acommercial motor vehicle (“CMV”) 104. Although the CMV 104 illustratedis a tractor configured to tow a trailer (not shown), the performancemonitoring system 100 can also be implemented in other types of CMV'ssuch as construction vehicles and agricultural equipment. The CMV 104includes an engine 108 that drives the CMV 104, and is controlled by anelectronic control unit (“ECU”) 112 that determines operatinginformation or parameters from the engine 108, and other parts of theCMV 104. Operating parameters monitored by the ECU 112 include speed,hours of service, operating status, ignition switch status, tripdistance, total vehicle distance, and the like.

The performance monitoring system 100 also includes an electronicon-board recorder (“EOBR”) base unit 116 that communicates with the ECU112 through an information bus 118 conforming to standards such as SAEJ1939 and SAE J1708 network buses. The base unit 116 has a plurality offunctions including, but not limited to, time keeping and data logging.In one implementation, the base unit 116 records and stores CMVinformation or data necessary to comply with FMSCA regulations such asthose mentioned above from the ECU 112. The performance monitoringsystem 100 also includes a portable device 120 such as a mobile phone, apersonal-digital-assistant (“PDA”), a laptop computer, or the like, thatcommunicates with the base unit 116. The base unit 116 communicates withthe portable device 120 through a cable or wireless link 122. The link122 may be a serial cable, such as a USB cable. Other exemplary linksinclude a wireless personal-area-network such as Bluetooth, and thelike. The portable device 120 generally supports multiple platforms suchas Windows Mobile 5 cell phones, Pocket PC 2003 (or better) PDA's, andcomputers such as laptops. The performance monitoring system 100 alsoincludes a remote host server 123 running a remote host application 124that wirelessly communicates with the portable device 120 via a networksuch as the Internet, detailed hereinafter. In some embodiments, aglobal position satellite (“GPS”) system 128 also communicates with theECU 112 and/or the base unit 116 so that information from the GPS system128 (such as time and location) is available to the CMV 104. In someembodiments, at least a portion of the information stored in the baseunit 116 or information communicated to and from the base unit 116 isencrypted.

FIG. 2 shows the base unit 116 in a block diagram format. As shown, thebase unit 116 includes a processor (such as a microprocessor, controlleror application-specific-integrated-circuit (“ASIC”)) 204. The base unit116 also includes a communication module 206, a real-time clock 210, anda display unit 212. In some embodiments, the base unit 116 includes amemory module 211 that stores CMV information. In some embodiments, thedisplay unit 212 includes a plurality of LED's 214 to indicate thestatus of the base unit 116, such as, a connection status that indicateswhether a portable device has been connected to the base unit 116, asystem status that indicates whether the base unit 116 is properlyfunctioning, a communication status that indicates if signals arecommunicated between the base unit 116 and the ECU 112, and a portabledevice communication status that indicates whether signals arecommunicated between the base unit 116 and a connected portable devicesuch as the portable device 120.

In some embodiments, the memory module 211 stores a log of dataretrieval history. For example, when a portable device such as theportable device 120 sends a request for data from the base unit 116, thebase unit 116 logs the request, retrieves the data from the memorymodule 211, and communicates or delivers the data to the connecteddevice. The memory module 211 also logs other information related to therequest, such as the time span over which data was retrieved, the timethe data was retrieved or time-stamped, and the size of the data thatwas delivered. In some embodiments, once the portable device hasretrieved the data, the memory area that stored the retrieved data ismarked extracted, transmitted, or downloaded, and is re-used, ifnecessary.

The communication module 206 includes an interface module 216 thatincludes a plurality of interfaces such as a USB interface 220, avehicle power interface 224, an optional Bluetooth interface 228, and aGPS interface 232. In some embodiments, the USB interface 220 includes aB-type USB socket connector into which a USB cable can be inserted toallow the base unit 116 to communicate with devices such as the portabledevice 120. The power interface 224 provides power filtering andconditioning to support operations from power obtained from the CMV 104.Furthermore, the USB interface 220 also allows the base unit 116 to befield-programmable, that is, the base unit 116 can be reconfigured,modified, or upgraded via the USB interface 220. The GPS interface 232supports a connection between an additional GPS board or device and thebase unit 116. In some embodiments, the GPS interface 232 also includesan antenna input to accommodate an antenna that may be required.

FIG. 3 shows an exemplary base unit 300 (116 of FIG. 2), wherein likereference numerals refer to like parts. The base unit 300 includes amicroprocessor 302 (204 of FIG. 2) that processes and outputs data asdescribed. For example, the microprocessor 302 is coupled to first andsecond transceivers 304, 308, respectively, to receive external data.The first transceiver 304 conforms to a J1708 standard, and transmitsand receives data through a CMV interface connector 310 (224 of FIG. 2),a J1708 communication bus 312, and a protection and filtering module316. The protection and filtering module 316 filters the received dataso that data noise can be reduced or eliminated. The protection andfiltering module 316 also ensures that the received data has apredetermined amplitude range that is acceptable to the microprocessor302. In this way, amplitude surges in data can be detected, and themicroprocessor 302 can be protected.

Similarly, the J1939 transceiver 308 transmits and receives data throughthe CMV interface connector 310, a J1939 communication bus 320, and asecond protection and filtering module 324. The second protection andfiltering module 324 filters out noise from the received data, andlimits an amplitude range of the received data. Both of the transceivers304 and 308 are regulated by a charge pump 328. In the embodiment shown,the base unit 300 receives its power from the CMV 104 through the CMVinterface connector 310 and a CMV power bus 332. The power is regulatedand surge-protected with a protection, filtering, and inrush limitcircuitry 336, a power supply circuit 340, and a voltage holdup circuit344.

A battery 348 supplies power to the real-time clock (“RTC”) 350 (210 ofFIG. 2) which provides a real-time clock function to allow software toaccurately determine a time with a predetermined resolution. In theembodiment shown, the resolution is 1 ms. In some embodiments, the RTC350 is required to remain operational while the CMV 104 does not providepower to the base unit 300.

In the embodiment shown, a flash memory 352 (211 of FIG. 2) is connectedto the microprocessor 302 to log a data retrieval history as describedearlier. The flash memory 352 also logs other information related to therequest, such as the time span over which data was retrieved, the timethe data was retrieved or time-stamped, and the size of the data thatwas delivered. The microprocessor 302 also displays the status of thebase unit 300 with a plurality of status light-emitting-diodes 356 (212of FIG. 2). The base unit 300 also includes a USB type B connector 360(220 of FIG. 2) to transmit and receive data through a USB connector ofan external portable device. The received data is also filtered andprotected with a USB protection and filtering module 364. To receive aGPS signal, the base unit 300 also includes a GPS antenna connector 368(232 of FIG. 2) to be connected to a GPS antenna. Data received throughthe GPS antenna connector 368 is similarly filtered and protected with aGPS protection and filtering module 372. A GPS receiver module 376 thenprepares the received data for further processing by the microprocessor302.

FIG. 3A shows an alternative embodiment of a base unit 380 (116 of FIG.2), wherein like numerals refer to like parts. The base unit 380includes the CMV interface connector 310 that connects to the CMV powerbus 332, and communicates to the ECU 112 (of FIG. 1) with the J1708communication bus 312 and the J1939 communication bus 320, via the firstand second transceivers 304, 308, respectively. The microprocessor 302processes and outputs data from the first and second transceivers 304,308. In the embodiment shown, the base unit 380 also includes the flashmemory 352, and a Bluetooth interface 384 (228 of FIG. 2) thatcommunicates with the mobile devices 120 that are capable of Bluetoothwireless communications. Also, the USB interface 360, as shown, includesa USB Mini-AB connector.

FIG. 4 shows an example of the portable devices 120 in the form of asmart phone 400 displaying a login screen 402. In such cases, the smartphone 400 wirelessly connects to the base unit 116 via Bluetooth orother wireless connections, or is wired to the base unit 116 via one ormore cables. The smart phone 400 includes a display 404 and generates agraphical user interface on the display 404. The graphical userinterface prompts operators for information and displays informationsuch as an hours-of-service of a particular operator and otherinformation, as detailed hereinafter. The smart phone 400 also includesan input keyboard 408 to allow operators to enter operator or driver,and trip information. The display 404, as shown in FIG. 4, via asoftware application installed in the smart phone 400 shows the loginscreen 402, and prompts the operator for login or identifyingcredentials such as identity or username at a username entry 412 and apassword at a password entry 416. Once the username and the passwordhave been entered and verified, the CMV driver or operator starts aperformance monitoring process. Initially, if there is no log entryattributed to the operator, the portable device 120 attempts toestablish a network connection with the remote host application 124. Inturn, the remote host application 124 verifies the identifyingcredentials, detailed hereinafter. After the remote host application 124has verified the identifying credentials, the remote host application124 passes back via a return parameter a validation signal to theportable device 120.

As shown in FIG. 5, after receiving a validation signal from the remotehost application 124, the smart phone 400 (via the softwareapplication), in a trip login screen 500, prompts the operator for tripinformation such as a tractor identification number at a tractor numberentry 504, a trailer number at a trailer number entry 508, and shipmentinformation at a shipment info entry 512. Similarly, as shown in FIG. 6in a location edit screen 600, the operator is prompted for a locationcode at a entry 604, and/or an actual location at entry 608.

FIG. 7 shows a time edit screen 700. Once logged on, the operator isalso allowed to edit a time entry 704, and/or a location entry 708 inthe time edit screen 700. FIG. 8 shows a status edit screen 800 in whichthe operator is allowed to add a new duty by selecting a new duty entry804 using the display 404 and the keyboard 408. After selecting the newduty entry 804, a status screen appears that allows the operator tofurther modify or update the status of his or her activities (forexample, in sleeper, driving, and the like), detailed hereinafter.

After CMV 104 is in motion, e.g., traveling down a road, the ECU 112monitors the distance traveled. As shown in an exemplary status screen900 of FIG. 9, once the CMV 104 has traveled a predetermined amount oftime and/or distance, it is assumed the CMV 104 is being driven to adesired destination rather than, for example, being moved from oneparking spot to another. Subsequently, the smart phone 400 displays acurrent status in the status field 904 to reflect changes in theoperator status (now “driving”). After the CMV arrives at a destinationand stops, the smart phone 400 prompts the operator for a newdestination location in the location entry 708 (of FIG. 7). Thisinformation is then stored in the memory module 211.

As shown in FIG. 10, the status screen 900 also includes a menu tab1002. When the menu tab 1002 is activated, the smart phone 400 displaysa menu 1003. In the embodiment shown, the menu 1003 includes a “Records”option 1004, a “Reports” option 1008, a “Team Driver” option 1012, a“Team Driver Share” option 1016, and a “File” option 1020. In someembodiments, the “Records” option 1004 allows a driver to access recordssuch as trip information, employee rules, and the like, and also allowsa driver to download records, certify and submit logs, identifyunassigned driving periods, and edit log locations, detailedhereinafter. In some embodiments, the “Reports” option 1008 allows adriver to generate or access information such as, for example, dutystatus, daily hours, failure reports such as vehicle failure reports,and location codes, some of which are detailed hereinafter. The “File”option 1020 allows a driver to change his or her password, enter theperformance monitor process into a road-side inspection mode, and checkfor updates such as trip updates, rule set updates, and the like.

When a driver activates the “Report” option 1008 and selects to displaythe duty status, the smart phone 400 displays the duty status asdiscussed, as shown in an exemplary duty status report screen 1104 ofFIG. 11. In the embodiment shown, the duty status report screen 1104summarizes all entries collected thus far. When the operator activates a“Detail” tab 1108 on the duty status report screen 1104, the smart phone400 displays details of the entries, as shown in a log detail screen1204 of FIG. 12. In the embodiment shown, the status report screen 1108lists information such as log date, tractor, trailer, shipment, drivertype, time zone, rule set, and distance traveled.

In some cases, a regulation enforcement officer can ask a CMV driver forhis or her driving logs for a predetermined number of days, such as, forexample, seven days, prior to the day of inquiry, or for a predeterminedamount of time, such as, for example, 168 hours, prior to the time ofinquiry. However, when the smart phone 400 is new, the smart phone 400may not have been configured to include existing logs of a particulardriver and/or a particular CMV. When the logs of interest are not storedin the smart phone 400, a CMV driver can use the smart phone 400 todownload the logs of interest from other places, such as, for example,the remote host server 123 via the Internet, and/or from the base unit116.

FIG. 13 shows the smart phone of FIG. 4 displaying a log download screen1300 which prompts a user to download one or more logs to the smartphone 400. Particularly, in the embodiment shown, the log downloadscreen 1300 includes a log date column 1304 which lists a plurality oflogs 1308 that are available for download, and their correspondingdates. Each of the available logs 13 has a corresponding check box 1312to accept an input selection from a user. In the embodiment shown, logs1308 from the last few days are available to be downloaded to the smartphone 400. In other embodiments, logs from additional periods of timeare also available to be downloaded to the smart phone 400. The logdownload screen 1300 also includes an “Exists” column 1316 whichindicates whether each of the logs 1308 in the log date column 1308exists, or has already been stored in the smart phone 400. In theembodiment shown, none of the available logs 1308 is stored in the smartphone 400. Once a user has checked one or more of the check boxes 1312and tabbed a download button 1320, the selected logs are downloaded tothe smart phone 400.

If the user tabs an OK button 1324 or the download button 1320 withoutselecting any of the logs 1308, the user is required to confirm that theuser has elected not to store any of the available and downloadable logs1308 to the smart phone 400. FIG. 14 shows the smart phone of FIG. 4displaying a confirmation screen 1400. In the embodiment shown, theconfirmation screen 1400 indicates that logs are missing, and promptsthe user to select between a “Yes” tab 1404 which confirms no logs aredownloaded, and a “No” tab 1408 which returns the display 404 fromscreen 1400 back to screen 1300.

When a CMV driver logs out of the performance monitoring process, he orshe is given an option of submitting any available logs in acertification process. In this way, the CMV driver can legally submitthe logs for regulation compliance purposes. Particularly, FIG. 15 showsthe smart phone of FIG. 4 displaying a logout screen 1500 of thecertification process on the smart phone 400. The logout screen 1500includes an “Actual Time Off Duty” dialog box 1504 allowing the CMVdriver to select an actual time that the CMV driver is off duty. In theembodiment shown, the CMV driver has selected to complete the submission“Now” in the dialog box 1504. Other options of the dialog box 1504include, but are not limited to, one hour, two hours, and the like. Theadditional time allows the CMV driver to conduct a post trip inspection,for example. After selecting a time for the dialog box 1504, the CMVdriver has to manually select on the logout screen 1500 to certify andsubmit logs by tapping a certify check box 1508, and/or to retain thelogs in the smart phone 400 by tapping a retain check box 1512. Afterselecting to certify the logs and/or to retain the logs, the CMV driverthen taps an “OK” tab 1516 to continue the certification process, or a“Cancel” tab 1520 to cancel the certification process.

After the driver has tapped the OK tab 1516 to continue thecertification process, the smart phone 400 displays a plurality of logsthat are available for submission and certification. FIG. 16 shows thesmart phone 400 of FIG. 4 displaying an exemplary log submission screen1600 which lists an available log in a log list box 1604. When the CMVdriver taps a “Submit” tab 1608, the smart phone 400 submits theavailable logs listed in the log list box 1604 and indicates that thecertification process is complete. FIG. 17 shows the smart phone 400 ofFIG. 4 displaying an exemplary log submission complete screen 1700.

FIG. 18 shows an exemplary screen 1800 of the remote host application124. Once the log is received at the remote host application 124, theremote host application 124 stores and calculates parameters such ashours-of-service information of the operator and alerts the operator orthe carrier of any violations of predetermined FMCSA rules. For example,a log summary area 1804 lists all duty entries the operator submittedthrough the portable device 120. A log information area 1808 lists otherdriver and vehicle parameters collected. The remote host application 124thus can rearrange the entries collected and generates different reportsas needed. Furthermore, if an operator has a non-compliance violation,the remote host application 124 will also transmit a signal back to theportable device 120 to alert the operator of the violation.

In the embodiment shown, the log information area 1808 lists a pluralityof log entries, such as, for example, a “Log Date” indicating a log dateof the received log, a “Total Miles” indicating a total mileage drivenby the operator, a “Driver Type” indicating a type of qualifications orrestrictions on a driver, for example, whether the driver is licensed todrive a property-carrying vehicle or a passenger-carrying vehicle orrestrictions apply based on the type of shipment or cargo, a “DriveReturned/Release From Duty” indicating whether the operator has returnedfrom duty or the operator has been released from duty, an “Off DutyHours” identifying an amount of time that the CMV driver is off duty, a“Sleeper Hours” indicating an amount of time that the CMV driver hasbeen on sleeper hours, a “Driving Hours” indicating an amount of timethat the CMV driver has been driving for the trip, an “On Duty Hours”indicating an amount of time that the CMV driver has been on duty, andan “Exempt Log” indicating if the submitted log can be exempted fromlogging. Similarly, the log summary area 1804 summarizes log entries fora trip administered by the CMV driver. For example, the summary area1804 lists entries such as, for example, a duty status, a time, aduration, and a rule set used by the CMV driver. In the embodimentshown, the rule set is “US 60 hour.” The CMV driver was off duty from12:00 AM to about 3:00 AM for about three hours. Afterwards, the CMVdriver was driving from 3:00 AM to about 6:00 AM for about three hours.The CMV driver was again off duty from 6:00 AM to about 01:00 PM forabout seven hours, and drove from 01:00 PM to about 06:00 PM for aboutsix hours. As such, the CMV driver drove for a total of about eighthours, as displayed in the Driving Hours entry of the log informationarea 1808. The screen 1800 is also expandable to display otherinformation such as, violations, locations (which indicates locationsthe CMV driver has traveled during the trip), team drivers (whichindicates a list of operators involved in the trip), and receipts (whichindicates a list of receipts collected during the trip).

Various features and aspects of embodiments of the invention are setforth in the following claims.

What is claimed is:
 1. A system for logging performance of a driveroperating a commercial motor vehicle (“CMV”), the system comprising: abase unit including a non-transitory computer-readable medium andconfigured to be mounted in the CMV, receive at least one operatingparameter from a controller in the CMV, and store the at least oneoperating parameter in the non-transitory computer-readable medium; anda portable device having a display and configured to communicate withthe base unit through a connection selected from the group consisting ofa wireless connection and a wired connection, generate a graphical userinterface on the display, to prompt the driver for identifyinginformation via the graphical user interface, receive identifyinginformation of the driver from the graphical user interface, receive theat least one operating parameter stored in the non-transitorycomputer-readable medium from the base unit, display driver compliancedata in the graphical user interface based, at least in part, on theidentifying information, to list a plurality of driver logs in thegraphical user interface based, at least in part, on the identifyinginformation, and wirelessly transmit one or more driver logs to a remotehost; wherein the base unit is further configured to store the at leastone operating parameter when the portable device is disconnected fromthe base unit.
 2. The system of claim 1, wherein the portable device isfurther configured to prompt the driver, via the graphical userinterface, for trip information and wherein the trip informationincludes at least one selected from the group consisting of a tractoridentification, a trailer number, shipment information, and a locationcode.
 3. The system of claim 1, wherein the portable device is furtherconfigured to list, via the graphical user interface, at least one ofselected from the group consisting of a log date, a driver type, a timezone, a rule set, and a distance traveled by the CMV.
 4. The system ofclaim 1, wherein the portable device is configured to selectivelydownload at least one log unavailable in the portable device.
 5. Thesystem of claim 1, wherein the portable device is further configured toprompt the driver, via the graphical user interface, for a newdestination location when the CMV reaches a destination based, at leastin part, on information from the base unit.
 6. The system of claim 1,wherein the portable device is further configured to generate an alertfor noncompliant performance of the driver.
 7. A logging system for acommercial motor vehicle (“CMV”) operated by a driver, the loggingsystem comprising: a base unit including a processor and non-transitorycomputer-readable medium and configured to be located in the CMV, beconnected to a controller monitoring at least one operating parameter ofthe CMV, and receive and store at least one operating parameter from thecontroller in the non-transitory computer-readable medium; a portabledevice having a display and configured to communicate with the base unitthrough a connection selected from the group consisting of a wirelessconnection and a wired connection, receive identifying information fromthe driver, receive, from the base unit, the at least one operatingparameter stored in the non-transitory computer-readable medium, displaycompliance data based, at least in part, on the identifying information,and to wirelessly transmit signals based on the compliance data,generate a graphical user interface on the display to prompt the driverfor the identifying information, to display a current status of thedriver, and to list a plurality of logs based, at least in part, on theidentifying information, and to selectively download at least one logunavailable in the portable device; and a remote host configured towirelessly receive the signals based on the compliance data; the baseunit storing the at least one operating parameter when the portabledevice is disconnected from the base unit.
 8. The system of claim 7,wherein the portable device is further configured to prompt the driver,via the graphical user interface, for trip information.
 9. The system ofclaim 8, wherein the trip information includes at least one selectedfrom the group consisting of a tractor identification, trailer number,shipment information, and location code.
 10. The system of claim 7,wherein the portable device is further configured to list at least oneselected from the group consisting of a log date, driver type, timezone, rule set, and distance traveled by the CMV on the display.
 11. Thesystem of claim 8, wherein the compliance data includes hours-of-servicedata.
 12. The system of claim 7, wherein the portable device is furtherconfigured to prompt the driver, via the graphical user interface, for anew destination location when the CMV reaches a destination based, atleast in part, on information from the controller and the base unit. 13.The system of claim 7, wherein the remote host is further configured togenerate an alert for noncompliant performance of the driver.
 14. Amethod for logging performance of a driver operating a commercial motorvehicle (“CMV”), the method comprising: connecting a base unit includinga processor and a non-transitory computer-readable medium to acontroller of a CMV; monitoring, with the base unit, at least oneoperating parameter of the CMV; connecting a portable device to the baseunit; generating a graphical user interface on a display of a portabledevice; receiving, via the graphical user interface, identifyinginformation for the driver; verifying the identifying information forthe driver; generating a trip screen, in the graphical user interface,to prompt the driver for trip information; displaying a current statusof the driver based, at least in part, on the identifying information;receiving at least one operating parameter of the CMV at the portabledevice through a non-portable base unit coupled to the portable device;displaying compliance data based, at least in part, on the identifyinginformation at the portable device; and wirelessly transmittingcompliance signals indicative of the compliance data from the portabledevice; selectively downloading to the portable device at least one logunavailable in the portable device; and storing the at least oneoperating parameter in the non-transitory computer-readable medium. 15.The method of claim 14, further comprising listing at least one of a logdate, driver type, time zone, rule set, and distance traveled by theCMV.
 16. The method of claim 14, wherein the compliance data includeshours-of-services data.
 17. The method of claim 14, further comprisingprompting the driver for a new destination location when the CMV reachesa destination based, at least in part, on data received from thecontroller and the base unit.
 18. The method of claim 14, furthercomprising: wirelessly receiving the compliance signals at a remote hostfrom the portable device; generating managing signals based on thereceived signals at the remote host; wirelessly transmitting managingsignals from the remote host to the portable device; wirelesslyreceiving the managing signals at the portable device; and managingperformance of the driver based on the received managing signals bylisting on the graphical user interface a plurality of logs based, atleast in part, on the identifying information.